Dr. Windows 3

home *** CD-ROM | disk | FTP | other *** search

/ Dr. Windows 3 / dr win3.zip / dr win3 / VISUALBA / PPM116.ZIP / PPM.DOC < prev next >

Wrap

Text File | 1994-02-17 | 78KB | 1,915 lines

Programmer's Project Manager (PPM) Copyright 1993 by Stevenson Technical Services, Inc. (STSI) 108 Second Avenue West Bertha MN 56437-0297 Phone: (218) 924-2050 FAX: (218) 924-2050 (Ext. 11) The Bertha BBS: (218) 924-2060, 8,N,1 ■─────────────────────────────────────────■ │ Welcome! │ ■─────────────────────────────────────────■ Thank you for trying PPM! PPM is a utility designed to make programming easier. Much easier! By setting up your own program in PPM, you can compile and link your source files, compress the resulting EXE file, date and time stamp selected release files, scan them for viruses, create a final compressed file in .ZIP, .ARJ, or .SQZ format, and copy any of the above categories of files to destination directories on any drive. PPM is meant to be a complete environment, helping you put together a program from start to finish. If you appreciate PPM, you are encouraged to call The Bertha BBS at (218) 924- 2060, and let us know! Comments, suggestions, and enhancement requests are always welcome! ■─────────────────────────────────────────■ │ Requirements │ ■─────────────────────────────────────────■ To run PPM reliably, you will need the following: ∙ DOS 3.3 or Higher ∙ IBM PC, PC-Compatible or MS-DOS Computer with a Hard Drive and 640K RAM ∙ CGA Color, EGA Color, or VGA Color Monitor (Highly Recommended) Page 1 ■─────────────────────────────────────────■ │ Table of Contents: │ ■─────────────────────────────────────────■ Title Page & Welcome . . . . . . . . . . . . . . . . . . . . . . . . Page 1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 1 Quick-Start Instructions . . . . . . . . . . . . . . . . . . . . . . Page 3 Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 3 Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 3 Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . Page 4 PPM's Feature List . . . . . . . . . . . . . . . . . . . . . . . . . Page 4 Installing PPM . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 6 Executing PPM . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 7 Using PPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 7 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . Page 7 The File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 8 The Project Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Page 10 The Compile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Page 12 The Link Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 13 The Utility Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Page 15 The Master Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Page 17 The Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 19 The Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 20 PPM Editor Commands . . . . . . . . . . . . . . . . . . . . . . . . Page 21 Troubleshooting / Common Problems . . . . . . . . . . . . . . . . . Page 25 Questions And Answers . . . . . . . . . . . . . . . . . . . . . . . Page 25 Programs Mentioned . . . . . . . . . . . . . . . . . . . . . . . . . Page 27 PPM Registration Form . . . . . . . . . . . . . . . . . . . . . . . Page 28 Page 2 ■─────────────────────────────────────────■ │ Quick-Start Instructions: │ ■─────────────────────────────────────────■ To get PPM up and running in a hurry, follow these Quick-Start instructions: 1. Run the Install program by logging to the correct drive and directory, and type "INSTALL". 2. After installing PPM, you should edit your AUTOEXEC.BAT file, and add the following statement: SET PPM=DRIVE:\PATH (Replace with your drive and path.) EXAMPLE: SET PPM=D:\PPM (Note: You do not need to edit your AUTOEXEC.BAT file if you accepted the default destination directory of "C:\PPM".) 3. Reboot your machine to ensure that the new changes to your AUTOEXEC.BAT file have taken effect. 4. Execute Programmer's Project Manger by typing "PPM". ■─────────────────────────────────────────■ │ Disclaimer: │ ■─────────────────────────────────────────■ By using PPM and/or any of its components, users indicate their acceptance of the following terms: "PPM is supplied as is. The author disclaims all warranties, expressed or implied, including, without limitation, the warranties of merchantability and of fitness for any purpose. Neither STSI, The Bertha BBS, or any STSI employees will be held responsible for any damages, direct or consequential, which may result from the use of PPM and/or any of its components." "Information in this documentation is subject to change without notice and does not represent a commitment on the part of STSI. STSI may make improvements and/or changes in this documentation or in the products and/or programs described in this documentation at any time." ■─────────────────────────────────────────■ │ Registration: │ ■─────────────────────────────────────────■ PPM is distributed under the shareware concept. It is NOT freeware! You may try PPM for a period of two weeks. After this period, you must either discontinue using it, or register it. A single-user license is only $49.95. This price includes printed documentation, 3 1/2" and 5 1/4" diskettes, and a registration number for PPM. By registering PPM and receiving a valid registration number, users will be able to automatically remove all program delays, and will be notified of Page 3 major product updates and revisions. To order PPM and receive a registration number, call STSI at (218) 924-2050, and charge it to your Visa, MasterCard, American Express, or Discover credit card. Upon request, you will receive a temporary registration number over the telephone. Using this number will automatically remove all delay screens from PPM. For further registration information and pricing, please read the REGISTER.DOC file included with PPM. There is also a registration form contained at the end of this documentation file. ■─────────────────────────────────────────■ │ Technical Support: │ ■─────────────────────────────────────────■ Technical support is available to PPM users through the following means: The Bertha BBS: New versions of PPM will be posted here as soon as they are available. The Bertha BBS uses a U.S. Robotics Dual- Standard Modem, which is capable of V.32bis, V.32, HST, and 2400 baud connect speeds. The access number for The Bertha BBS is (218)-924-2060. Technical support questions should be addressed to the SYSOP. STSI FAX: STSI has a FAX machine on-line 24 hours-a-day to accept FAX transmissions. Technical support questions / problems may be faxed to (218) 924-2050. Most FAX transmissions will be automatically routed to the FAX machine. If you have problems reaching our FAX machine, wait until after the first ring, press 11, and then begin transmitting. Telephone: Technical support calls may be placed at (218) 924-2050. ■─────────────────────────────────────────■ │ PPM's Feature List │ ■─────────────────────────────────────────■ PPM makes programming easier. Much easier! By setting up your own program in PPM, you can perform any or all of the following tasks: 1. Edit source, documentation, or release files directly from PPM. * Choose an editor from a master list, or customize the editor name, path, and switches as you need them. * Optionally use PPMEDIT, a built-in (64K-limit) text editor with a multiple document interface, and other powerful features. * Optionally pass the name of a source, documentation, or release file to edit, so your editor can pre-load it. 2. Compile all, selected, or changed source files. Page 4 * Choose the project compiler from a master list, or customize the compiler name, path, and switches as you need them. * Optionally pause after each compile, last compile, or disable pausing. 3. Link all source files. * Choose the project linker from a master list, or customize the linker name, path, and switches as you need them. * Select any combination of libraries to include from a master list. * Set the name of the executable file to be created, and specify the first file to be listed in the linking process. * Optionally specify the second file to be listed in the linking process. * Optionally pause after linking, or disable pausing. * Optionally create a link map file. * Optionally compress the EXE file immediately after linking. 4. Compress the executable file. * Choose the EXE compressor from a master list, or customize the compressor name, path, and switches as you need them. * Optionally pause after compressing the EXE file, or disable pausing. 5. Date and time stamp the release files. * Enter a specific date and time to place on selected release files. * PPM allows version tracking, and displays the program's version number on the date/time stamping screen. 6. Virus scan the release files. * Choose the virus scanner from a master list, or customize the scanner name, path, and switches as you need them. * Optionally pause after scanning each file, the last file, or disable pausing. 7. Compress the release files for distribution. * Choose the project compressor from a master list, or customize the compressor name, path, and switches as you need them. * Optionally pause after compressing the project files, or disable pausing. * Specify the name and path of the compressed file to be created. * Use PKZIP, ARJ, or SQZ to compress the release files. Page 5 8. Update files to destination directories. * Optionally copy the source files, documentation files, release files, executable file, or compressed file to one or more destination directories during PPM's update routine. This is especially helpful for backing up precious data, or creating a master directory full of your program's files. 9. Create a master program. * Optionally perform any one or more of the previously listed events in sequence. 10. Print any or all of the project files. * Print files directly from PPM, or route them to an external printing utility. (Useful for laser printers and utilities that can print 2-up on a laser printer.) 11. Run the executable file directly from PPM. * Optionally specify run arguments (command line parameters) to be passed during the execution process. 12. Other features... * Create a master list of compilers, linkers, libraries, editors, EXE compressors, virus scanners, and project compressors. PPM supports an unlimited number of entries in each category. * Create project files in one of three categories: source files, documentation files, or release files. PPM supports an unlimited number of files in each category. Create default directories for each category of files. * Optionally use PPM's optimum shell routines to swap PPM to disk or EMS when executing an external program. * Mouseable interface makes PPM fast and easy to use! Why use PPM? It does everything except write the programming code for you! ■─────────────────────────────────────────■ │ Installing PPM │ ■─────────────────────────────────────────■ The files needed to properly install PPM are listed in the file PACKING.LST. Log to the drive where you are installing PPM from, and type "INSTALL". The installation program will ask you where you are installing PPM from (usually, the current directory), and the location where the program files should be stored. (The default destination directory is C:\PPM.) PPM can be installed on any drive in your system, including network drives. Page 6 Important! Be sure to include a "SET PPM=N:\PPM" statement (or wherever you put PPM), in your AUTOEXEC.BAT file. If this environment variable is not found, PPM defaults to using the C:\PPM sub- directory. ■─────────────────────────────────────────■ │ Executing PPM │ ■─────────────────────────────────────────■ To execute PPM, type "PPM" from the \PPM sub-directory, and press [ENTER]. PPM's desktop will display the main menu, along with a logo containing version and copyright information. ■─────────────────────────────────────────■ │ Using PPM │ ■─────────────────────────────────────────■ PPM has a user-friendly interface to make working with project files as easy and seamless as possible. PPM supports the use of either the mouse or the keyboard. Persons using the keyboard will want to become familiar with the keys and key combinations available for use within PPM. They are as follows: HOME Move to beginning of field CTRL+HOME Move to beginning of field END Move to end of field CTRL+END Move to end of field INSERT Insert Mode / Overstrike Mode DELETE Remove character over the cursor BACKSPACE Remove character left of the cursor LEFT ARROW Move cursor one character to the left RIGHT ARROW Move cursor one character to the right ENTER Move cursor to the next field TAB Move cursor to next field SHIFT+TAB Move cursor to previous field ALT+DOWN ARROW Show list on drop-down list box DOWN ARROW Select next entry in drop-down list box UP ARROW Select previous entry in drop-down list box SPACE BAR Highlight file in file list box ■─────────────────────────────────────────■ │ Getting Started │ ■─────────────────────────────────────────■ To start working with PPM, you will need to set up your defaults under the Setup menu. This should always be the place to start, since all other project settings depend on what is set up under the Setup Menu. Modify each of the options on the Setup screen as they apply to you. For information on what each of the options on the Setup screens mean, see "The Setup Menu", explained below. After you have set up the PPM program defaults, you can create your first project. The following steps will assist you in creating a new project file. 1. Select New Project from the File menu, fill in each of the fields, and select Ok. Page 7 2. Select Project Paths from the Project menu, and enter the default path where your source, documentation, and release files will be maintained. The source path should be the location of the files that will be compiled and linked. The documentation path should be the location where text (information) files will be created and edited. The release path should be the location of the files that will released with the project. These files can be optionally date and time stamped, scanned for viruses, and included in a compressed project file. 3. Select Project Editors from the Project menu, and set up the default editors you will be using for each set of files. 4. Select Manage Project Files from the Project menu, and add the names and paths of the files you want included in each group. 5. Select Compiler from the Compile menu, and choose the default compiler you will be using with the current project. 6. Select Linker from the Link menu, and choose the default linker you will be using with the current project. 7. Select Libraries from the Link menu, and mark each of the library names that you want included in the linking process. 8. Select EXE Filename / Link Files from the Link menu, and specify the name and path of the executable filename to be created, the first file to be listed in the link response file, and, optionally, the second file to be listed in the link response file. 9. Select EXE Compressor from the Link menu, and choose the default EXE Compressor you will be using with the current project. 10. Select Virus Scanner from the Utility menu, and choose the default Virus Scanner you will be using with the current project. 11. Select Project Compressor from the Utility menu, and choose the default Project Compressor you will be using with the current project. 12. Select Setup Update Routines from the Master menu, and enter the paths where each of the listed file groups should be copied during the update routine. 13. Select Save Project from the File menu to save your project file with your customized settings. Taking the steps listed above will help you to get started on your own project with PPM. Once each of these steps has been completed, you should be prepared to use any of PPM's features. ■─────────────────────────────────────────■ │ The File Menu │ ■─────────────────────────────────────────■ New Project: Selecting New Project allows the creation of a new PPM project file in .PPM format. When this option is selected, a screen will display prompting you for the filename, project description, and version number. When entering the project's version number, only enter the numeric representation of the Page 8 version. For example, type "1.05", not "Version 1.05". (PPM displays the version number on the date/time stamp screen to assist you when stamping your release files.) Open Project: Opening a project allows an existing project file to be opened for use on the desktop. The starting drive and directory for opening files is the default path for .PPM files, as specified in the Setup PPM Path screen. Close Project: Closing a project file removes it from use on the desktop, and disables all related menu items until another project file is created or opened. If any changes have not been saved to the project file, PPM will warn you and give you the option to save them before closing. Save Project: Saving a project file places all of your current settings into a .PPM file, allowing you to recall them for later use. Among the information stored in a .PPM file is the list of source, documentation, and release files, and the names, paths, and switches of the compiler, linker, scanner, compressors, libraries, and editors you have selected as the default for your project. Save Project As: Selecting Save Project As allows a project to be saved under a new filename, maintaining all of the default settings already set up in the source project file that is being copied. Print Processor: This option can be selected to choose a print processor for the open project file. PPM allows direct printing of source, documentation, and release files, but also offers the option of routing files to an external print processor. This can be useful for printing your files in a custom fashion, such as printing source files 2-up on a page using a laser printer. The list of available external print processors depends on the ones you set up on the Setup Defaults screen. Print: When this option is selected, PPM displays the printing screen. One file can be printed at a time, with the option of sending it directly to the printer port (LPT1, LPT2, or LPT3) or to a file, or the file can be routed through an external print processor, as set up under the Print Processor option explained above. (Note: Network users experiencing errors when printing should see the Troubleshooting section toward the end of this documentation.) Delete Project: Selecting Delete Project allows an existing project file to be deleted from the drive. The starting drive and directory for deleting files is the default path for .PPM files, as specified in the Setup PPM Path screen. Page 9 Shell To DOS: PPM's Shell To DOS feature is handy for programmers who need to perform other functions in the middle of using PPM. PPM can do a standard Shell To DOS, or it can use a special Optimum Shell routine that swaps PPM out to EMS or to disk. (Default Optimum Shell options can be specified on the Setup Optimum Shell Options screen.) Using the Optimum Shell option provides more available memory to execute other programs, etc. Exit PPM: When you are ready to exit PPM, you can select Exit PPM from the File menu. Before exiting, PPM will warn you if your project file contains unsaved changes, offering you the option to save them before exiting. PPM will then close the project file, and display a confirmation message before exiting. (Mouse users can double-click on the close box located in the top left corner of the PPM title bar to execute the Exit PPM command.) ■─────────────────────────────────────────■ │ The Project Menu │ ■─────────────────────────────────────────■ Project Information: Project Information can be accessed to change information that was specified when a .PPM file was originally created. This allows the drive, path, filename, project description, and/or version number to be changed at any time in the process of developing a program. Project Paths: The Project Paths screen contains three separate default paths for the project files. There is one path for the source files, one for the documentation files, and one for the release files. The paths that are set up here will determine the default location of each of these files. Since this is only a default, alternate paths can be specified on any of the related files. Specifying paths in these locations simply makes data entry easier and faster. Project Editors: Default editors for the source files, documentation files, and release files can be set up under the Project Editors option. PPM offers three different editing options. The first option is to use PPM's Real-Mode editor, called PPMEDIT.EXE, which is the default. PPMEDIT is a simple, but well-written text editor with a 64-K limit. The second option is to use PPM's Protected-Mode editor, which requires a 286 or higher. The third option is to use an external, user-defined editor. When you select an external editor, PPM displays a drop-down list box with the names of all of the editors you set up on the Setup Defaults screen. This allows you to quickly choose the one that will best-suit your current project files. Since there are three separate file groups, a different editor can be specified for source, documentation, and release files, allowing maximum flexibility when creating a complete project. Page 10 Manage Project Files: This menu item will be, perhaps, one of the most used menu items within PPM. Through the Manage Project Files screen, you will manage all of the files contained in the open project. File Group: This drop-down list box contains a list of the three file groups used by PPM. The three groups are 1) Source Files, 2) Documentation Files, and 3) Release Files. Each of the groups has their own list of included files. The Source Files group should contain a list of each of the files that will be compiled and linked with the project. The Documentation Files group should contain a list of each of the text (information) files that are considered to be part of the project. This may include a revision history, technical notes, on-line documentation files, and more. The Release Files group should contain a list of all of the files that will be released with the final project. Files listed in this group may be date and time stamped, scanned for viruses, and/or added to a final compressed project (archive) file. Included Files: The Included Files list box displays a list of each file maintained in the currently selected group. When the File Group changes, the list of displayed files also changes. The files maintained in the Included Files list are sorted alphabetically, making them easier to locate. A counter at the bottom of this list box shows the number of files located in the currently selected File Group. Add: The Add command button may be selected to add a new entry to the current File Group. The file being added does not need to reside on the hard drive in order for it to be added to the project. If necessary, it can be added first and created later. A Browse command button is available on this screen to assist you in finding the correct file to add. The file that is added MUST contain a full drive and path pointing to the new file. If you attempt to add a file without a drive specification, PPM automatically prepends the default drive and path for the currently selected File Group, as set up on the Project Paths screen, explained earlier. The new file must also contain an extension. If the file you are entering does not use an extension, simply place a period (".") at the end of the name. Modify: The Modify command button is similar to the Add command button, but instead of adding a new entry, Modify allows you to change the name and/or path of the file that is currently selected in the Included Files list box. Modify only works when the highlight bar is visible over the top of a file in the Included Files list box. Edit: One of the benefits of PPM is that you can automatically execute the editor of your choice from within PPM. There is no need to exit the PPM environment to edit your source, documentation, or release files. When this command button is selected, PPM invokes the editor set up under Project Editors, and passes the name of the selected file to the editor. Most text editors can interpret this passed parameter, and automatically load the named file. Edit New: If the file you wish to edit is not listed in the Included Files list, or if your editor cannot handle the filename as a passed parameter, use the Edit New command button. This simply executes the editor set up under Page 11 Project Editors, without passing a filename. Edit All: If you have selected the PPM Editor to edit the files in one of the File Groups, you should notice that this command button is enabled. The PPM environment works in conjunction with the PPM Editor to automatically attempt to load all of the files listed in a specific file group. While this may not be possible in some projects due to the size and/or number of files listed, other projects may be able to use this very powerful feature. Any time that the selected editor is not the PPM Editor, PPM will disable this command button, making it unavailable for use by any other editor. Remove: The Remove command button can be selected to remove a file from the list of Included Files. A message box will display before performing this action, allowing you to cancel your selection, or continue to remove the file. Ok: Once you have performed any needed actions on the list of Included Files, you can select the Ok command button to return to the main menu. Mouse users can also double-click on the close box. Run Arguments: This screen allows the user to enter a sequence of command line parameters to be passed to the program when it is executed by using the Run Program statement explained below. Unlike other programs, PPM saves the run arguments into the .PPM project file, so PPM "remembers" and uses these same arguments until you change them or remove them completely. Run Program: This option allows the created program to be executed directly from the PPM environment. This allows quick and easy testing of the code, without the need to exit and re-enter PPM. If run arguments were specified as explained above, PPM passes these as parameters to the executed program. PPM can execute the program using a standard DOS Shell command, or it can use a special Optimum Shell routine that swaps PPM out to EMS or to disk. (Default Optimum Shell options can be specified on the Setup Optimum Shell Options screen.) Using the Optimum Shell option provides more available memory to the program being executed. ■─────────────────────────────────────────■ │ The Compile Menu │ ■─────────────────────────────────────────■ Compiler: This option can be selected to choose a project compiler for the open project file. The list of available compilers depends on the ones you set up on the Setup Defaults screen. If you want to enter your own compiler on-the-fly, you can simply type in the necessary name, path, and switches that will be needed to properly execute the compiler. Page 12 Note: For programmers using Builder (made by Hyperkinetix, Inc.), you should specify "-c" on the switches command line to make sure that Builder does not attempt to automatically link the project files. Compiler Preferences: The Compiler Preferences screen contains the setting for whether PPM should force the compiler to pause after each file is compiled, after the last file is compiler, or not to pause at all. Pausing after each compile allows programmers to troubleshoot problems in their code while debugging it. Pausing after the last compile is also handy to simply pause at the end of the compiling process. If you are relatively sure that you will not encounter any errors during the compiling process, you may want to disable pausing, which will force PPM to restore the screen immediately after the last file is compiled. The compiler preferences screen also contains a check box which, when selected, will force PPM to issue a beep-beep-beep whenever a pause is issued. Compile All Modules: When Compile All Modules is selected from the compile menu, PPM executes the project compiler (see above) and passes the name of each source file maintained in the project. Users can optionally specify if they want to pause after each file is compiled, after the last file is compiled, or disable pausing by setting the desired option on the Compiler Preferences screen as explained above. Compile Changed Modules: When Compile Changed Modules is selected from the compile menu, PPM executes the project compiler (see above) and passes the name of each source file to be compiled that has changed since the last time it was compiled. If a .OBJ file from a previous compile cannot be found, PPM automatically compiles the file, creating a new module. This is definitely one of the most useful features of PPM. Programmers are not forced to remember the names of the modules that need to be recompiled. PPM does it automatically. Users can optionally specify if they want to pause after each file is compiled, after the last file is compiled, or disable pausing by setting the desired option on the Compiler Preferences screen as explained above. Compile Selected Modules: Selecting Compile Selected Modules from the compile menu causes a screen to display with a list of all source files in the current project. Programmers can click in the check box next to the listed file to select a file, and select Compile to compile the selected source files in the project. A counter in the lower right corner of this screen displays the total number of files listed, along with the number of user-selected files. PPM maintains a list of the selected source files, and writes these to the .PPM file. The next time you choose to Compile Selected Modules, PPM automatically checks the same ones you selected the last time you used this routine. Compile Changed And Link: This command allows the fastest possible creation of an executable file by only compiling the files that have changed, and automatically linking the resulting modules. This is the same as selecting Compile Changed Modules from Page 13 the Compile Menu, and Link All Modules from the Link Menu. Compile All And Link: This command allows the fast creation of an executable file by compiling all of the files in the project, and automatically linking the resulting modules. This is the same as selecting Compile All Modules from the Compile Menu, and Link All Modules from the Link Menu. ■─────────────────────────────────────────■ │ The Link Menu │ ■─────────────────────────────────────────■ Linker: This option can be selected to choose a project linker for the open project file. The list of available linkers depends on the ones you set up on the Setup Defaults screen. If you want to enter your own linker on-the-fly, you can simply type in the necessary name, path, and switches that will be needed to properly execute the linker. Linker Preferences: The Linker Preferences screen contains several linker settings that determine actions taken during and after the link process. The first setting determines whether PPM should force a pause after the linking process is complete, or not to pause at all. Pausing after the linking process will display an brief message, and will allow you to view any error messages reported by the linker, while suppressing the pause will force PPM to restore the screen immediately after the linking process is complete (whether or not it was successful). The linker preferences screen also contains a check box which, when selected, will force PPM to issue a beep-beep-beep whenever a pause is issued. The linker preferences screen also allows programmers to specify if a map file should be created during the linking process, and if so, what it should be called. If the last option on this screen is checked, PPM is instructed to use the selected EXE compressor (see below) to automatically compress the EXE file after the linking process is complete. Libraries: The Libraries screen allows programmers to select any number of pre-defined libraries that should be included in the file linking process. To include libraries in the linking process, a check mark must be placed beside the desired library name on this screen. To set up a list of available libraries in PPM, enter the Setup Defaults menu, and specify the libraries you will be using. (See "The Setup Menu" described below.) EXE Filename / Link Files: On the EXE Filename / Link Files screen, programmers can specify the names of the 1) the executable file to be created, 2) the first link file to be listed in the link response file, and 3) the second link file to be listed in the link response file. The executable file can be created in any directory, and can have any valid DOS filename. The link files must be in .OBJ format, and they are not required to be part of the list of current source files in Page 14 the project. Most of the time, programmers only need to specify the name of the first link file in the project, but a need may arise to specify the name of the second link file. We recommend not using the second link file field unless your program requires it. Each of the three drop-down boxes on this screen allow the user to choose a name from the list of source files in the project. If a user selects an executable filename from the list of .OBJ files, PPM will change the extension of the file in this field to .EXE when the user moves the cursor to another field. (Note: The executable filename field and the first link file field MUST contain entries in order for PPM to attempt to link the source (.OBJ) files.) Link All Modules: When Link All Modules is selected from the link menu, PPM executes the project linker (see above) and passes the name of a link response file that is used in the linking process. The link response file contains the names of the project's source files, the name (and location) of the executable file, the name (and location) of the map file (if one exists), and the names (and locations) of the libraries being linked into the file. Users can optionally specify if they want to pause after the linking process is complete, or disable pausing by setting the desired option on the Linker Preferences screen as explained above. The map file can also be specified on the Linker Preferences screen. To specify Libraries, the executable filename, and the first and second link files, see the options explained above. EXE Compressor: This option can be selected to choose an EXE Compressor for the open project file. The list of available EXE Compressors depends on the ones you set up on the Setup Defaults screen. If you want to enter your own EXE Compressor on- the-fly, you can simply type in the necessary name, path, and switches that will be needed to properly execute the EXE Compressor. Compress EXE File: When your executable file has been successfully created through the linking process, you may want to compress it using an EXE compression program. Selecting this option from the link menu invokes the project's EXE compressor, as specified above, to compress the executable file. PPM automatically pauses after the process is complete so you can review any results. ■─────────────────────────────────────────■ │ The Utility Menu │ ■─────────────────────────────────────────■ Date / Time Stamp Release Files: Selecting Date / Time Stamp Release Files from the Utility menu will display a screen with a list of all the current release files. The PgUp and PgDn command buttons can be used to search through the list if there are more present than are currently being shown on the first page. On the right side of the screen, PPM contains two text fields allowing programmers to enter the date and time that should be used to stamp the selected files. Once Stamp is selected, PPM saves the list of date and time stamped files to the project file, allowing them to be automatically marked as the default the next time this routine is used. A message will display while the files are being stamped, and completion message will show up when the process has been finished. Page 15 Virus Scanner: This option can be selected to choose a virus scanner for the open project file. The list of available virus scanners depends on the ones you set up on the Setup Defaults screen. If you want to enter your own virus scanner on- the-fly, you can simply type in the necessary name, path, and switches that will be needed to properly execute the virus scanner. Scanner Preferences: The Scanner Preferences screen contains the setting for whether PPM should force the virus scanner to pause after each release file is scanned, after the last release file is scanned, or not to pause at all. Pausing after each scan allows programmers to view any error messages reported by the virus scanner. You can disable pausing during or after the scanning process, which will force PPM to restore the screen immediately after the last file is scanned. The scanner preferences screen also contains a check box which, when selected, will force PPM to issue a beep-beep-beep whenever a pause is issued. Scan All Release Files: When Scan All Release Files is selected from the utility menu, PPM executes the project scanner (see above) and passes the name of each release file maintained in the project. Users can optionally specify if they want to pause after each file is scanned, after the last file is scanned, or disable pausing by setting the desired option on the Scanner Preferences screen as explained above. Scan Selected Release Files: Selecting Scan Selected Release Files from the utility menu causes a screen to display with a list of all release files in the current project. Programmers can click in the check box next to the listed file to select a file, and select Scan to scan the selected release files for viruses. A counter in the lower right corner of this screen displays the total number of files listed, along with the number of user-selected files. PPM maintains a list of the selected release files, and writes these to the .PPM file. The next time you choose to Scan Selected Release Files, PPM automatically checks the same ones you selected the last time you used this routine. Project Compressor: This option can be selected to choose a Project Compressor for the open project file. The list of available Project Compressors depends on the ones you set up on the Setup Defaults screen. If you want to enter your own Project Compressor on-the-fly, you can simply type in the necessary name, path, and switches that will be needed to properly execute the compressor. (Note: Currently, PPM supports the use of ARJ, SQZ, and PKZIP to compress project files. LHA cannot be used at this time due to its lack of support for list files.) Project Compressor Preferences: The Project Compressor Preferences screen contains several compressor settings that determine actions taken during and after the compression process. The first setting determines whether PPM should force a pause after the compression process is complete, or not to pause at all. Pausing after the Page 16 linking process will display a "Strike any key to continue..." message, and will allow you to view any error messages reported by the project compressor, while suppressing the pause will force PPM to restore the screen immediately after the compression process is complete (whether or not it was successful). The project compressor preferences screen contains a check box which, when selected, will force PPM to issue a beep-beep-beep whenever a pause is issued. This screen should also contain the name of the compressed file to be created during the compression process. Compress All Release Files: When Compress All Release Files is selected from the utility menu, PPM executes the project compressor (see above), and passes a filename with a list of each release file maintained in the project. Users can optionally specify if they want to pause after the compression process is complete, or disable pausing by setting the desired option on the Project Compressor Preferences screen as explained above. Compress Selected Release Files: Selecting Compress Selected Release Files from the utility menu causes a screen to display with a list of all release files in the current project. Programmers can click in the check box next to the listed file to select a file, and select Compress to add the selected release files into a compressed project file with the filename set up on the Project Compressor Preferences screen. A counter in the lower right corner of this screen displays the total number of files listed, along with the number of user-selected files. PPM maintains a list of the selected release files, and writes these to the .PPM file. The next time you choose to Compress Selected Release Files, PPM automatically checks the same ones you selected the last time you used this routine. ■─────────────────────────────────────────■ │ The Master Menu │ ■─────────────────────────────────────────■ Setup Update Routines: The Setup Update Routines screen is a useful feature of PPM that allows programmers to copy the newest files (listed in the File Groups) to several different locations on the disk drive. File Group: In addition to the standard three file groups (Source Files, Documentation Files, and Release Files), this drop-down list box contains two more groups, called Executable File, and Compressed Project File. Copy Group Files To Directory / Directories: In this list box, programmers can enter one or more destination directories where files in each of the files groups are copied. This is especially useful for making a backup copy of your programming files to another drive, or updating alternate directories with the newest version of your program file. The number of directory entries for each file group is limited only by memory. A list of the destination directories for each file group is saved and maintained in the individual project file. Page 17 Add: The Add command button may be selected to add a new destination directory to the current File Group. A Browse command button is available on this screen to assist you in finding an existing directory. Modify: The Modify command button is similar to the Add command button, but instead of adding a new entry, Modify allows you to change the drive and/or path of the destination directory that is currently selected in the Copy Group Files To Directory / Directories list box. Modify only works when the highlight bar is visible over the top of a destination directory. Remove: The Remove command button can be selected to remove a destination directory from the list. A message box will display before performing this action, allowing you to cancel your selection, or continue to remove the entry. Ok: Once you have performed any needed actions on the list of destination directories, you can select the Ok command button to return to the main menu. Mouse users can also double-click on the close box. Update Files: The Update Files menu option actually performs the task of updating files to the destination directories, as set up under Setup Update Routines, described above. This screen presents five check boxes, allowing users to select any or all of the five file groups to update. When Ok is selected the update process begins, and a message displays the current file being copied, and the destination of the copied file. If PPM is unable to copy the current file, it issues an error message, explaining which file could not be copied, and where its destination directory should have been. Reasons for an error can range from the original file not existing, or not being found, to the destination directory not being present. Once the updating process is complete, PPM informs you with a message box. Create Master Program: This feature presents PPM's "icing on the cake". Create Master Program allows you to complete any or all of the operations performed during the normal routine of creating a program. This includes compiling all, changed, or selected modules, linking all modules, compressing the executable file, date and time stamping the release files, scanning all or selected release files for viruses, compressing all or selected release files into a compressed project file, and updating selected file groups to the previously set up destination directories. Each of these operations are optional, allowing you to exclude any of them from the master process. Using this menu options causing PPM to perform all of the selected operations in succession, improving the speed of the process. While parts of the process may be automatic, some routines may require user intervention, such as compiling selected modules, date and time stamping files, scanning selected release files, compressing selected release files, and updating. Of course, if you have selected any of the pausing options on the various preferences screens, PPM will issues the pause statements at the pre-selected places. Page 18 ■─────────────────────────────────────────■ │ The Setup Menu │ ■─────────────────────────────────────────■ PPM Path: To modify the default location for .PPM files, select PPM Path from the Setup menu. The path specified here will be the default for where the Open Project, Save Project As, and Delete Project dialog boxes display files when performing any of these actions. Defaults: The Setup Defaults screen is the heart and soul of PPM. This is where each of the utilities you will be using is set up. There are eight categories of utilities that can be created, and each category can have as many utilities as are needed. The categories are as follows: Compilers Project Compressors Linkers Virus Scanners Libraries Editors EXE Compressors Print Processors Every utility entered can have a Utility Name, Default Path, and Default Switches (except on Libraries, which do not use switches). Each of the available utilities listed can be modified or removed at will, allowing complete flexibility with any utilities you may be using. Add: The Add command button may be selected to add a new utility to the current utility group. A name and path MUST be specified in order for PPM to accept the new entry as valid. A Browse command button is available on this screen to assist you in finding an existing program. If you select a file from the browse screen, PPM pastes the filename, along with its drive and path, into the Path text box. Modify: The Modify command button is similar to the Add command button, but instead of adding a new entry, Modify allows you to change the name, path and/or switches of the utility that is currently selected in the list box. Modify only works when the highlight bar is visible over the top of a utility name. Remove: The Remove command button can be selected to remove a utility from the list. A message box will display before performing this action, allowing you to cancel your selection, or continue to remove the utility. Ok: Once you have performed any needed actions on the list of utilities, you can select the Ok command button to save the changes to the PPM.INI file, and return to the main menu. Cancel: If you do not wish to save changes that have been made to this screen, you can select the Cancel command button to return to the main menu. Any changes that have been made will be lost. Page 19 Optimum Shell Defaults: The Optimum Shell Defaults screen is used to select when and where PPM's optimum shell will be used. The optimum shell routine works by swapping PPM out to EMS or to disk, allowing more available conventional memory for executing compilers, linkers, etc. If optimum shell is not selected (check- marked), PPM uses a standard DOS shell, which leaves very little available conventional memory for the execution of other programs. PPM's optimum shell feature can be used for the following routines: * DOS Shell (Available from the File menu) * Compiling Source Files (Available from the Compile menu) * Linking Source Files (Available from the Link menu) * EXE File Compression (Available from the Link menu) * Virus Scanning (Available from the Utility menu) * Project Compression (Available from the Utility menu) * Program Execution (Available from the Project menu) * External PPM Editor (Available from the Manage Project Files Screen) * External (User-Selected) Editor (Available from the Manage Project Files Screen) * External Print Processor (Available from the File menu) Register: Selecting Register from the Setup Menu will allow users to enter a Registration Name and Number which will register their copy of PPM. This will automatically eliminate any built-in nag screens and accompanying delays. In addition to removing all program delays, registered users will receive the latest version of PPM on diskette, along with a printed manual, and will be notified of major product updates and revisions. To register PPM, call STSI at (218) 924-2050, and charge it to your Visa, MasterCard, American Express, or Discover credit card. Upon request, you will receive a registration number over the telephone. Using this number will automatically remove all delay screens from PPM. For further registration information and pricing, please read the REGISTER.DOC file included with PPM. There is also a registration form contained at the end of this documentation file. ■─────────────────────────────────────────■ │ The Help Menu │ ■─────────────────────────────────────────■ About PPM: This screen displays version and copyright information about Programmer's Project Manager, and how to contact STSI, the author of PPM. Page 20 Registration Info: This screen display ordering information for PPM, including payment methods and telephone numbers. For further registration information, please read REGISTER.DOC, included in this package. ■─────────────────────────────────────────■ │ PPM Editor Commands │ ■─────────────────────────────────────────■ PPM's Big Editor (for files larger than 64K), contains many useful commands for editing files. The following is a summary of these commands: Primary Keys Purpose <^J><^C> Copies the currently marked block to the clipboard area. Unmarks the block but leaves the text stream alone. <^J><^K> Copies the currently marked block to the clipboard area, and deletes the block from the main text stream. <^J><^P> Pastes the contents of the clipboard (if any) into the main text stream at the current cursor position. Cursor Movement <Left>, <CtrlS> Cursor left one character. Wraps to previous line if the WrapAtLeft option is in effect. <Right>, <CtrlD> Cursor right one character. <CtrlLeft>, <CtrlA> Cursor left one word. Wraps to end of previous line. <CtrlRight>, <CtrlF> Cursor right one word. Wraps to beginning of following line. <Home>, <CtrlQ><S> Cursor to beginning of line. <End>, <CtrlQ><D> Cursor to end of line. <Up>, <CtrlE> Cursor up one line. <Down>, <CtrlX> Cursor down one line. <CtrlW> Scroll display up one line. <CtrlZ> Scroll display down one line. <PgUp>, <CtrlR> Scroll display up one page. <PgDn>, <CtrlC> Scroll display down one page. <CtrlHome>, <CtrlQ><E> Move cursor to top of edit window. Page 21 <CtrlEnd>, <CtrlQ><X> Move cursor to bottom of edit window. <CtrlPgUp>, <CtrlQ><R> Move cursor to beginning of file. <CtrlPgDn>, <CtrlQ><C> Move cursor to end of file. <CtrlJ><L> Prompts the user for a line number, then moves the cursor to the specified line. Insertion and Deletion <Del>, <CtrlG> Delete character at cursor. <Bksp>, <CtrlH>, <CtrlBksp> Delete character to left of cursor. If the cursor is at the beginning of a line, it will be joined with the previous line. <CtrlY> Delete current line. <CtrlQ><Y> Delete from cursor to end of line. <CtrlT> Delete word to right of cursor. If the cursor is at end of line, the following line is joined with the current line. <Enter>, <CtrlM> Start a new line. <CtrlN> Insert a new line at the position of the cursor. <Tab>, <CtrlI> Move the cursor to the next tab stop. If insert mode is on, any text to the right of the cursor is shifted to the right. When fixed tabs are in effect, tab stops occur at 8-column intervals (by default). When smart tabs are in effect, tab stops are determined by the locations of the words on the previous line. <CtrlP> Insert control character. File Commands <F2>, <CtrlK><S> Save the current file and continue editing. <F3> Load a new file. <CtrlK><Q> Quit editing; ignore any changes made to the text. <CtrlK><D> Save the current file and load a new one. <CtrlK><N> Save the current file under a new name. <CtrlK><X> Save the current file and exit. Block Commands <F7>, <CtrlK> Mark the beginning of a block. Page 22 <F8>, <CtrlK><K> Mark the end of a block. <CtrlK><T> Mark the current word as a block. <CtrlQ> Jump to the beginning of the currently marked block. <CtrlQ><K> Jump to the end of the block. <CtrlK><H> Toggle the display of blocks. <CtrlK><C> Copy the currently displayed block to the position of the cursor. The block markers are placed around the new copy of the block. <CtrlK><V> Move the currently displayed block to the position of the cursor. <CtrlK><Y> Delete the currently displayed block. <CtrlK> Indent the currently displayed block by a fixed number of spaces (defaults to 2). Does nothing if the cursor is not within the block. <CtrlK> Unindent the block. <CtrlO><O> Toggle the case of all characters in the currently displayed block, or of the character at the cursor if not within a visible block. <CtrlO> Convert characters to upper case. <CtrlO><V> Convert characters to lower case. <CtrlK><R> Reads a file into the text buffer at the current position of the cursor and marks it as a block. If the entire contents of the file will not fit into the buffer, a warning will be generated and no data will be read in. <CtrlK><W> Writes the currently marked and displayed block to a file. <CtrlK> Writes the currently marked and displayed block to the printer: LPT1 by default, or the one set by calling SetPrinter. Search and Replace <CtrlQ><F> Allows the user to search for any string of up to 30 characters. After entering a search string, the user is prompted for search options, which include 'B' (search Backwards), 'G' (search Globally), 'L' (search Locally, within marked block), and 'U' (ignore case). <CtrlQ><A> Works like Search, except that the user is asked for a replacement string of up to 30 characters. In addition to the search options available for ccSearch, 'N' may be used to Page 23 indicate that replacements are to be made without asking for confirmation. If 'N' is not selected, each replacement must be confirmed: yes (make the replacement), no (don't make it), all (make this replacement and continue making replacements without further confirmation), and quit (stop the whole operation). <CtrlL> Repeat the last search or replace operation. Text Markers <CtrlK><0>..<CtrlK><3> Sets one of the ten text markers at the position of the cursor. The default command table does not assign any keys to SetMark4..SetMark9. <CtrlQ><0>..<CtrlQ><3> Moves the cursor to a text marker set with one of the ccSetMarkX commands. <CtrlK><M> Toggle the display of text markers. <CtrlQ> Jump to the last cursor position before the cursor was moved to the current line. Text Formatting <CtrlB> Reformat the current paragraph. Does nothing if word wrap is off. <CtrlK><G> Reformat the entire text buffer. Use with caution! <CtrlO><C> Center the current line between column 1 and the right margin. Mode Toggles and Option Settings <Ins>, <CtrlV> Toggle insert mode on or off. A fat cursor indicates insert mode; a thin cursor indicates overtype mode. <CtrlO> Toggle auto-indent mode on or off. In auto- indent mode, pressing <Enter> will cause the new line to have the same indentation as the previous line. <CtrlO><W> Toggle word wrap on or off. <CtrlO><F> Toggle the tab mode between smart tabs and fixed tabs. <CtrlO><T> Prompts the user for the number of columns between tab stops (1-10). <CtrlO><R> Prompts the user for a new right margin. <CtrlO> Prompts the user for the number of spaces to Page 24 indent/unindent marked blocks. The default value is 2. Other <CtrlQ><L> Restore original contents of the current line. <F1>, <ClickBoth> Request help. <ClickLeft> Moves the cursor to the position indicated by the mouse. ■─────────────────────────────────────────■ │ Troubleshooting / Common Problems: │ ■─────────────────────────────────────────■ Problem #1: After printing a text file directly to the printer, network users may receive the error, "An error occurred while attempting to print the selected file." This is not a problem with PPM, but rather a quirk when using a network. Even though the file is printed correctly to the right port, the network can send an errorlevel back to DOS, causing this error message. This is not serious, and should not interfere with the printing process at all. ■─────────────────────────────────────────■ │ Questions And Answers │ ■─────────────────────────────────────────■ Question #1: What compilers, linkers, compressors, etc. have been tested with Programmer's Project Manager? Answer: Although most compilers, linkers, virus scanners, and EXE compressors should work with PPM, these are the ones that have been specifically tested with PPM, and appear to work without any problems. Compilers: BC.EXE (Visual Basic for DOS) BLD.EXE (Builder) Linkers: LINK.EXE (Visual Basic for DOS) MLINK.EXE (Builder) EXE Compressors: DIET.EXE (Diet) PKLITE.EXE (PK-Lite) TINYPROG.EXE (TINYPROG) Virus Scanners: SCAN.EXE (Scan) Project Compressors: ARJ.EXE (ARJ) PKZIP.EXE (PKZIP) SQZ.EXE (SQZ) External Print Processors: 4PRINT.EXE (4-Print) MW-LASER.EXE (MW-Laser) Page 25 Note: A problem has been noted that MW-Laser does not handle PPM's method of printing when command line parameters are passed to MW-Laser. PPM passes parameters first, and the filename second. MW-Laser wants these parameters in reverse order, causing MW-Laser to pause and request a filename to print. PPM will attempt to deal with this problem in a future release. Question #2: Does PPM take any precautions against losing information maintained in the individual .PPM files? Answer: Yes. When working in-depth with PPM, you may notice that the "Writing Project File..." message box will show up prior to performing certain critical operations. PPM automatically saves the project file prior to performing any of the following operations: Compiling Changed Modules Compiling Selected Modules Compiling All Modules Linking All Modules Scanning Selected Modules Scanning All Modules Compressing Selected Modules Compressing All Modules Saving the project file prior to performing these operations protects your information against the possibility of "crashes" which may occur from time to time, due to running external programs. In addition, PPM also detects whether or not the project file is saved prior to running the program (from the Project menu). If it is not saved, it offers the option of whether or not to save it before continuing. Question #3: What is the difference between "pre-switches" and "post- switches" when setting up default external editors? Answer: The pre-switches and post-switches fields are a new feature in version 1.10 of PPM. Pre-switches are command line switches, or parameters, that are sent to the editor prior to the filename to be edited, while post-switches are command line switches, or parameters, that are sent to the editor after the filename to be edited. In version 1.00 of PPM, the command line to invoke an external editor looked similar to this: Editor Switches Filename (Editor was the full path of the external editor; Switches were the command line parameters that were sent, as set up under the project editors screen, and Filename was the name of the file that was to be edited.) While most text editors accept the command line switches when they are placed before the filename, the text editor we use inside our company requires the use of switches to be placed AFTER the filename. The command line to invoke an external editor in version 1.10 of PPM looks similar to this: Page 26 Editor Pre-Switches Filename Post-Switches In the event that either the pre-switches or the post-switches are blank, a null (or blank) string is sent to the editor. In the event that a filename is not passed, the pre-switches and post-switches are sent without the filename to separate them. ■─────────────────────────────────────────■ │ Programs Mentioned │ ■─────────────────────────────────────────■ ARJ is copyrighted by Robert K Jung. Builder is copyrighted by Hyperkinetix, Inc. LHA is copyrighted by Haruyasu Yoshizaki. MS-DOS is copyrighted by Microsoft. PKLITE is copyrighted by PKWARE, Inc. PKUNZIP is copyrighted by PKWARE, Inc. PKZIP is copyrighted by PKWARE, Inc. SQZ is copyrighted by Jonas I Hammarberg. Visual Basic for DOS is copyrighted by Microsoft. Page 27 Stevenson Technical Services, Inc. (STSI) 108 Second Avenue West Bertha, MN 56437-0297 Phone: (218) 924-2050 FAX: (218) 924-2050 (Ext. 11) The Bertha BBS: (218) 924-2060, N,8,1 Programmer's Project Manager Registration Form Qty Description Price Each Total _____ PPM Single-User Registration $49.95 ________ Includes Printed Manual, 3 1/2" & 5 1/4" Diskettes _____ PPM Site-License (Users? ____) _______ ________ ┌────────────┬─────────────┐ ┌────────────┬─────────────┐ │ # of Users │ Price │ │ # of Users │ Price │ ├────────────┼─────────────┤ ├────────────┼─────────────┤ │ 5 │ $150.00 │ │ 50 │ $1000.00 │ │ 10 │ $300.00 │ │ 100 │ $1500.00 │ │ 20 │ $500.00 │ │ More? │ CALL │ └────────────┴─────────────┘ └────────────┴─────────────┘ _____ Additional Copies of Printed Manual $10.00 ________ Sub-Total: ________ Minnesota Residents Add 6.5% Sales Tax: ________ Total: ________ Name: ___________________________________ Title: ______________________ Company: __________________________________________________________________ Address: ______________________________ City: ____________________________ State: ___________ Zip Code: _______________ Phone: ___________________ Please Register PPM To This Name: _________________________________________ Method of Payment: ___ Visa/MC ___ American Express ___ Discover ___ Check/Money Order Enclosed (Checks/MO's must be in U.S. Funds drawn on a U.S. Bank!) Credit Card #: __________________________________ Expiration Date: ___/___ Name on Card: _______________________ Signature: _________________________ Comments / Suggestions: ___________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ Page 28 Please take a minute to answer the following questions. Your answers will assist us in improving and marketing PPM. (Check all that apply.) Where did you hear about PPM? [ ] BBS [ ] Catalog/Magazine [ ] Friend/Relative [ ] Other What operating systems / environments do you use? [ ] DOS [ ] Windows [ ] DESQview/DESQview/X [ ] OS/2 What features of PPM do you use? [ ] Compiling [ ] Linking [ ] EXE Compression [ ] Date/Time Stamping [ ] Virus Scanning [ ] Project Compression [ ] Updating Files [ ] Printing [ ] Program Execution What programming language(s) do you use? [ ] BASIC [ ] C / C++ [ ] Pascal [ ] Assembler [ ] Builder [ ] Other (Please specify) _________________________ What is the name of your... Compiler? __________________________ Linker? ____________________________ EXE Compressor? ____________________ Virus Scanner? _____________________ Project Compressor? ________________ Printing Utility? __________________ What feature(s) do you like the most about PPM? _________________________ __________________________________________________________________________ __________________________________________________________________________ What feature(s) would you like to see added to PPM? _____________________ __________________________________________________________________________ __________________________________________________________________________ Additional Comments: ____________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ May We Quote You? [ ] Yes [ ] No [ ] Doesn't Matter Page 29